Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1609

reference
540-tree-1
name
1609
tree-preservation-order

undefined

540-tpo-1
uprn
address-text
point
POINT (-1.023497 50.883999)
geometry
MULTIPOLYGON (((-1.023440 50.883993,-1.023443 50.884004,-1.023451 50.884014,-1.023463 50.884022,-1.023479 50.884027,-1.023496 50.884029,-1.023514 50.884028,-1.023530 50.884023,-1.023543 50.884015,-1.023551 50.884005,-1.023554 50.883994,-1.023551 50.883983,-1.023544 50.883973,-1.023531 50.883965,-1.023515 50.883959,-1.023498 50.883957,-1.023480 50.883959,-1.023464 50.883964,-1.023452 50.883972,-1.023443 50.883982,-1.023440 50.883993)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL